Skip to content

Feat/toxic flow tux #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 16 commits into from
Jul 18, 2025
Merged

Feat/toxic flow tux #65

merged 16 commits into from
Jul 18, 2025

Conversation

mmilanta
Copy link
Contributor

@mmilanta mmilanta commented Jun 19, 2025

Big refractor.
Now the cli tool just sends the mcp configuration signature to the backend, and gets back a list of Issue. printer.py then just prints the mcp configuration displaying the issues. Some extra issue are found locally.
The list of issues is:

  • E001: Tool poisoning, prompt injection
  • E002: Tool poisoning, cross server interaction
  • E003: Tool poisoning, hijack agent beheviour
  • W001: Tool poisoning, suspicious word used (as important, critical)
  • W003: Entity has changed. Possible rug pull attack
  • TF001: Data leak toxic flow detected.
  • TF002: Destructive toxic flow detected.

On top the X errors signify that something went wrong during the check.

  • X001: Could not reach analysis server
  • X002: Whitelisted

@mmilanta mmilanta force-pushed the feat/toxic-flow-TUX branch from b5600b3 to 5aaad14 Compare June 20, 2025 08:02
@mmilanta mmilanta merged commit 5ea95ef into main Jul 18, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants